Description

This pull request includes several changes to the civicsignalblog application, primarily focusing on using Path aliases for cleaner imports.

Additionally, it fixes failing build-next due to ESLint that were noted after merging #901.

While trying to use path aliases, it was noted that Payload does not resolve the paths as expected, this is dicussed here.

Thus, to resolve this we have:

• Added tsconfig-paths library and updated the dev script with -r tsconfig-paths/register enabling ts-node to correctly resolve path aliases defined in tsconfig.json
• Added a custom function in tsconfigPathToWebpackAlias.ts that create path aliases that are used in payload.config.ts
• Added tsc-alias and updated the build-next script to include tsc-alias -p tsconfig.server.json that replaces alias paths with relative paths after typescript compilation.

P.S
The PR might have many modified files but they are mainly adding aliases. The main concern with this PR is the use of two new packages as a workaround to the Path Alias Issue. While it's not ideal, it appears to be the most viable solution for now. Perhaps we can discover a better approach during our review.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation